                     Messaging Gateway JMS sample

This sample sets up a "round-trip" JMS propagation to illustrate both
outbound (AQ->MQ) and inbound (MQ->AQ) propagation. An outbound propagation
job moves messages from the AQ queue MGWUSER.JMS_TEXTQ to a user supplied
WebSphere MQ queue. An inbound propagation job moves messages from the
same user supplied WebSphere MQ queue to the AQ queue
MGWUSER.JMS_TEXTT. The end result should be messages moved from
MGWUSER.JMS_TEXTQ to MGWUSER.JMS_TEXTT.

Files 
----------
  create_users.sql
     Creates Oracle database users, MGWUSER, MGWAGENT, MGWADM needed for
     this sample

  create_queues.sql
     Creates AQ queues needed for this sample.

  jms_adm_setup.sql
     Configures Messaging Gateway objects for propagating messages.
     This file must be altered by the user before it can be run.

  setup.sql
     Allows setup of this sample to be accomplished in one step. It calls
     create_users.sql, create_queues.sql, jms_adm_setup.sql

  jms_adm_cleanup.sql
     Removes the Messaging Gateway configuration for this sample.

  drop_queues.sql
     Removes the AQ queues used for this sample.

  drop_users.sql
     Drops the Oracle database users used for this sample.

  jms_enq.sql
     Enqueues a fixed message into the AQ queue used as the source for
     message propagation.


Configuring and running sample -- All files are SQL scripts
--------------------------------------------------------------
  1. Edit the script jms_adm_setup.sql (or a copy).
     There will be a block that looks as follows:
        --
        -- WARNING!!!! The values below must be set before this script is run.
        --
        begin
          :gv_database         := '';    -- database specifier for agent user
          :gv_mq_queue_manager := '';
          :gv_mq_queue_name    := '';
          :gv_mq_channel       := '';
          :gv_mq_host          := '';
          :gv_mq_port          := '';
          :gv_mq_username      := ''; -- MQ user name
          :gv_mq_password      := ''; -- MQ user password
          :gv_mq_inbound_log_queue := '';
          :gv_mq_outbound_log_queue := '';
        end;

     Edit this block to include the appropriate values for these properties
     used for configuring a Messaging Gateway connection to WebSphere MQ.
     These values must refer to valid WebSphere MQ entities.

  2. As user, SYS as SYSDBA, run the script, setup.sql, to create the users
     MGWUSER, MGWAGENT, and MGWADM, create the AQ queues used by this sample,
     and configure Messaging Gateway objects for propagating messages.

  3. As user, MGWADM (password mgwadm), start the Messaging Gateway agent

     e.g.  exec dbms_mgwadm.startup;

     Check the MGW_GATEWAY view and the log file (in ${ORACLE_HOME}/mgw/log) 
     to determine the status of the Messaging Gateway agent.

     e.g.  select agent_name, agent_status from MGW_GATEWAY;

  4. As user MGWUSER (password MGWUSER), enqueue a (fixed) message to the
     propagation source queue by running the script, jms_enq.sql.

  5. As a user MGWADM, check that the message has been propagated

     e.g.  select job_name, propagated_msgs, failures from MGW_JOBS;

     This will show the number of messages that have been propagated for
     each propagation job since the Messaging Gateway agent was started.

Cleaning up the sample:
--------------------------------------------------------------
  1. As user MGWADM, before shutting down the Messaging Gateway agent, run
     the script, jms_adm_cleanup.sql, to clean up the MGW configuration.

  2. As user MGWADM, shut down the Messaging Gateway agent.

     e.g. exec dbms_mgwadm.shutdown

  3. When the Messaging Gateway agent is shut down, if desired, run the
     script, drop_queues.sql, to remove all AQ queues created for this sample.

  4. Connect as SYS as SYSDBA and run drop_users.sql to remove Oracle 
     schemas created for this sample.
